Prepare for v0.12.0 release #983
Conversation
Signed-off-by: Tobias Klauser <[email protected]>
|
just taking a note here, it's probably better to update the release process so that stable.txt gets updated after the release is available. currently there is a small time window where the stable.txt points to a non-existing version. |
Good point. Let's change |
Update stable.txt only after the new version was tagged and released. Otherwise, there is a small time window where stable.txt would point to an inexistent version. Ref. #983 (comment) Suggested-by: Michi Mutsuzaki <[email protected]> Signed-off-by: Tobias Klauser <[email protected]>
Done in #992 |
Update stable.txt only after the new version was tagged and released. Otherwise, there is a small time window where stable.txt would point to an inexistent version. Ref. #983 (comment) Suggested-by: Michi Mutsuzaki <[email protected]> Signed-off-by: Tobias Klauser <[email protected]>
Update stable.txt only after the new version was tagged and released. Otherwise, there is a small time window where stable.txt would point to an inexistent version. Ref. cilium#983 (comment) Suggested-by: Michi Mutsuzaki <[email protected]> Signed-off-by: Tobias Klauser <[email protected]>
Update stable.txt only after the new version was tagged and released. Otherwise, there is a small time window where stable.txt would point to an inexistent version. Ref. cilium/cilium-cli#983 (comment) Suggested-by: Michi Mutsuzaki <[email protected]> Signed-off-by: Tobias Klauser <[email protected]>
No description provided.